What is the quickest and most comprehensible way to explain to a non-programmer what commented-out code is? When I mentioned it in a conversation to non-programmers, they seemed lost.

Such people could for instance be graphical designers, when working on the same team to make an application. Typically I would need to mention what I will be/currently am working with during an update meeting.

At first I thought about substituting commented-out with unused code. While it is true to some degree, it is also very ambiguous.

If you are wondering, I am working with legacy code with commented-out code.

This leads to my question: "how do you explain commented-out code to a non-programmer?"